Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

React roadmap document? #11645

Closed
International opened this issue Nov 23, 2017 · 3 comments
Closed

React roadmap document? #11645

International opened this issue Nov 23, 2017 · 3 comments
Labels
Type: Discussion

Comments

@International
Copy link

Do you want to request a feature or report a bug?
A feature

What is the current behavior?
I think many people would be interested in a document that would show the future/long term plans for React, and features that are planned.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar
It's not a bug.

What is the expected behavior?
Document or link exists in repo, and can be accessed to see what is planned for the future.

Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?
N/A
@gaearon
Copy link
Collaborator

gaearon commented Jan 2, 2018

The truth is we don’t really have a long-term roadmap.

Watching and participating in https://github.com/reactjs/rfcs is probably the best way to stay informed on changes we’re making in the next months.

@gaearon gaearon closed this as completed Jan 2, 2018
@gaearon
Copy link
Collaborator

gaearon commented Nov 29, 2018

https://reactjs.org/blog/2018/11/27/react-16-roadmap.html

@tobiasbueschel
Copy link

Hi @International & @gaearon,

Just to follow up with this discussion, I wonder whether we'd like to consider GitHub's Projects feature for any roadmap and release planning? Create React App also started using it recently.

Advantages
I think this could help to improve transparency and collaboration within the React community. For example, non-core members could easily identify pending issues for upcoming releases, and could offer more targeted support. Thereby, potentially shortening our release cycles.

Disadvantages
This of course only works if the project board is well maintained, which would have to be done by a core member.

Examples

We could also use GitHub Projects for general (1) issue triaging or (2) pull request management, which a few other projects are already doing:

In addition to the default automation that GitHub already provides, one could perhaps even create custom card automation using GitHub's Projects API: https://developer.github.com/v3/projects/cards/#move-a-project-card

Keen to hear what you both think ☺️

Cheers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Type: Discussion
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@gaearon @International @tobiasbueschel